chore: keep uv.lock in sync automatically - #248
Merged
Conversation
uv.lock kept drifting behind pyproject.toml because nothing updated the two together. There were two sources for that: - Dependabot ran as the `pip` ecosystem, which only knows pyproject.toml. Switching to the `uv` ecosystem makes it maintain both files in one PR. - The release workflow bumped the version in pyproject.toml without re-locking, so uv.lock still claimed 1.9.0 while the project was at 1.9.1. It now runs `uv lock` and commits the result along with it. To keep this from silently coming back, `make qa` now verifies via `uv lock --check` that the lockfile matches pyproject.toml. Also refresh uv.lock, which was still on 1.9.0 from the last release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F3ADPwk11GHQF7BBwQHaPz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
uv.lockkept drifting behindpyproject.toml, so it had to be refreshed by hand in three of the four dependency PRs merged today. There are two independent causes:1. Dependabot ran as the
pipecosystem. That ecosystem only understandspyproject.tomland never touchesuv.lock— which is why #243, #245 and #247 landed with a stale lockfile. Dependabot has supporteduvnatively since March 2025; it reads and updates both files together. The group names were renamedpip-*→uv-*to match.2. The release workflow bumped the version without re-locking. It rewrites
versioninpyproject.tomlviasedand commits only that file. After the 1.9.1 release,uv.lockstill declaredversion = "1.9.0"for the project itself. It now runsuv lockand commits the result alongside.Guard against regressions.
make qagained averify-lockstep runninguv lock --check, so any future drift turns the build red instead of going unnoticed — no matter whether it comes from Dependabot, the release pipeline or a manual edit.Verified locally:
make verify-lockfails on a deliberately introduced drift and passes on the refreshed lockfile.🤖 Generated with Claude Code
https://claude.ai/code/session_01F3ADPwk11GHQF7BBwQHaPz